Use type index for now, and prep 0.4.2 release #24
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
After getting some errors in Subxt, I realised that older metadata produced with versions of scale-info prior to 2.11.1 and using the
retainmethod (ie anything that's had pallets/runtime APIs stripped out of it) would produce panics inscale-typegen. So, for now, let's revert to using the type index rather than ID to avoid breaking using Subxt etc against older metadata files.Tested this against subxt with pre-2.11.1 metadatas and it seemed to be ok, whereas without it you run into panics (unless you update artifacts)